Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@agentic/src/nodes/base.ts`:
- Around line 159-163: The code currently always emits an error workflow message
via emitWorkflowMessage with type KaiWorkflowMessageType.Error regardless of the
emitResponseChunks flag; update the error emission in the function/method that
calls emitWorkflowMessage so that it checks the existing emitResponseChunks
boolean (or a new emitErrors option) before sending errors to the workflow
stream—i.e., wrap the emitWorkflowMessage(...) error call in if
(emitResponseChunks) { ... } or if (emitResponseChunks || emitErrors) { ... }
and propagate/define emitErrors where needed (caller sites like
summarizeAdditionalInformation, summarizeHistory, planFixes) so internal
"thinking" operations that set emitResponseChunks:false do not surface errors
unless explicitly allowed.

In `@tests/e2e/enums/output.enum.ts`:
- Around line 1-4: The test enum forces a single exact label for CoreExtension
which breaks branded variants; update the OutputChannels handling so tests
accept both formats instead of a single string — e.g. return or export a
matcher/array that includes both `${extensionShortName} Core Extension` and the
legacy/long-name variant (or switch test lookup to use startsWith/contains
against extensionShortName). Modify the exported OutputChannels.CoreExtension
usage (and any tests that import it) to use the new flexible matcher/array so
E2E channel selection is robust across branded builds.

In `@vscode/go/src/goExternalProviderManager.ts`:
- Line 53: The spawn invocation that starts the external provider (this.process
= spawn(...)) passes an undocumented "-name generic" flag; remove the "-name"
argument and only pass supported flags (e.g., "-socket",
this.providerSocketPath), and instead ensure the provider identification is set
in provider_settings.json (name: "generic") or via the provider configuration
API used by go-external-provider; update the code that constructs the argument
array in goExternalProviderManager (the spawn call) to match the binary's
documented CLI and add/verify provider_settings.json creation or loading logic
so the provider name is configured there.

---

Nitpick comments:
In @.husky/pre-commit:
- Around line 5-6: The pre-commit hook unconditionally overwrites NVM_DIR which
breaks non-standard NVM installs; update the .husky/pre-commit script so it
preserves an existing NVM_DIR and only falls back to $HOME/.nvm when undefined
(use shell parameter expansion for NVM_DIR), then source "$NVM_DIR/nvm.sh" as
before; reference the NVM_DIR variable and the existing source line to locate
and modify the code.